Expere Engine and Tools Change Log Entries

Expere Engine Release: 2017.1External release date is TBD. Expere Engine build number is: 2017.1.0.4369

SignerID issue resolved
  • Type: Defect
  • Reference: PBI 458310
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: It was reported that SignerID was being returned with no string value present, where in pervious versions they were either given a string or 'null' value. This caused corresponding breaking changes to related processes.
Solution: This issue has been resolved; SignerID now returns either a string or 'null' value in the Expere response file.
Implementation Notes: This feature requires a 2017.1 Expere Engine update.
Previously failing transactions now generate normally
  • Type: Defect
  • Reference: PBI 457641
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: An issue was identified that caused transactions to fail when using eSignature functionality. It was determined that a missing element existed in the base functionality.
Solution: This issue has been resolved.
Implementation Notes: This defect correction requires a 2017.1 Expere Engine update.
Expere Engine change log updated with 2017.1 schema information
Summary: Our Expere Engine change now includes information regarding any schema additions and updates, allowing our users to identify schema changes between releases. We have created a new Schema Changes section on the Change Log and Important Notifications page for each release.
Implementation Notes: This new feature is available in the 2017.1 release.
Expere now updated to support latest versions of Microsoft Windows and SQL
Summary: The Expere Engine has been tested to validate that it functions properly with Windows Server 2016 and SQL 2016.
Implementation Notes: This feature requires a 2017.1 Expere Engine update. For more information, consult the Expere System Requirements guide: Windows Environment Software Requirements.
Package functionality added to Select, SelectAndGenerate, and Generate API's
Summary: We have enhanced the Select, SelectAndGenerate, and Generate API's to accept custom packages through a new <InlinePackage/> parameter within each of these API's. This allows users to create or modify one or multiple custom packages for a particular line of business or precedence unit by selecting documents from one or more package or autoselection rules.
Implementation Notes: Consider the following:
eSignature Field Order enhancement
  • Type: Enhancement
  • Reference: PBI 444854
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: We modified the method for applying enumerated values to the <eSignature/> fields so that the sequencing method always assigns the highest value in the sequence of each signer to their respective <Type>Signature</Type> fields, hence making the Signature field the last field in the order.
Technical Notes: Here is an example response:
-<r:SignaturePointSet>
  -<r:Signer>
    <r:Id>null</r:Id>
    <r:SignerEmail>firstlast@test.com</r:SignerEmail>
    <r:Description>null</r:Description>
    -<r:SignaturePoints>
      -<r:SignaturePoint>
        <r:IncludeDate>true</r:IncludeDate>
        <r:PageNumber>1</r:PageNumber>
        <r:PageOrder>null</r:PageOrder>
        <r:Height>36.0</r:Height>
        <r:Width>198.0</r:Width>
        <r:SignatureText>null</r:SignatureText>
        <r:XCoordinate>36.0</r:XCoordinate>
        <r:YCoordinate>566.84</r:YCoordinate>
        <r:Type>Signature</r:Type>
        <r:FieldName>WKES_Signaturefirstlast@test.com_2</r:FieldName>
        <r:Sequencing>2</r:Sequencing>
      </r:SignaturePoint>
      -<r:SignaturePoint>
        <r:IncludeDate>false</r:IncludeDate>
        <r:PageNumber>1</r:PageNumber>
        <r:PageOrder>null</r:PageOrder>
        <r:Height>36.0</r:Height>
        <r:Width>50.0</r:Width>
        <r:SignatureText>null</r:SignatureText>
        <r:XCoordinate>238.0</r:XCoordinate>
        <r:YCoordinate>566.84</r:YCoordinate>
        <r:Type>Date</r:Type>
        <r:FieldName>WKES_Datefirstlast@test.com_1</r:FieldName>
        <r:Sequencing>1</r:Sequencing>
      </r:SignaturePoint>
    </r:SignaturePoints>
  </r:Signer>
  -<r:Signer>
    <r:Id>null</r:Id>
    <r:SignerEmail>_first_last@test.com</r:SignerEmail>
    <r:Description>null</r:Description>
    -<r:SignaturePoints>
      -<r:SignaturePoint>
        <r:IncludeDate>true</r:IncludeDate>
        <r:PageNumber>1</r:PageNumber>
        <r:PageOrder>null</r:PageOrder>
        <r:Height>36.0</r:Height>
        <r:Width>198.0</r:Width>
        <r:SignatureText>null</r:SignatureText>
        <r:XCoordinate>309.6</r:XCoordinate>
        <r:YCoordinate>566.84</r:YCoordinate>
        <r:Type>Signature</r:Type>
        <r:FieldName>WKES_Signature_first_last@test.com_2</r:FieldName>
        <r:Sequencing>2</r:Sequencing>
      </r:SignaturePoint>
      -<r:SignaturePoint>
        <r:IncludeDate>false</r:IncludeDate>
        <r:PageNumber>1</r:PageNumber>
        <r:PageOrder>null</r:PageOrder>
        <r:Height>36.0</r:Height>
        <r:Width>49.99997</r:Width>
        <r:SignatureText>null</r:SignatureText>
        <r:XCoordinate>511.6</r:XCoordinate>
        <r:YCoordinate>566.84</r:YCoordinate>
        <r:Type>Date</r:Type>
        <r:FieldName>WKES_Date__first_last@test.com_1</r:FieldName>
        <r:Sequencing>1</r:Sequencing>
      </r:SignaturePoint>
    </r:SignaturePoints>
  </r:Signer>
</r:SignaturePointSet>
Implementation Notes: This enhancement requires picking up the Expere Engine 2017.1 release. and setting the <eSignatureWKES/> option to "true."
WKES Sign Date Naming Convention
  • Type: Enhancement
  • Reference: PBI 442435
  • Compliance Impacts: This item iis not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: The WKES Sign Date fillable field naming convention has been updated from WKES_date to WKES_signdate.
Implementation Notes:No user action is required.
eSignature Enhancements
  • Type: Defect
  • Reference: PBI 440808
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue:

We have updated the field name elements for the eSignature and eSignatureDate within the PDF and ExpereResponse file as part of the SignaturePointSet element.

The eSignature field name has been updated to no longer include the borrower name, additionally, the eSignatureDate field name for Static content has been updated to be consistent with Dynamic content.

Solution:

The specific changes to the eSignature and eSignatureDate field names are captured below.

Before:

eSignature Field Name: SIG_Borrower_1_1_true_1_BobbyBorrower_BW1Name.eSig

eSignatureDate Field Name: BW1Name.eSig.eSigDate

After:

eSignature Field Name: SIG_Borrower-1_1_true_1_BW1Name.eSig

eSignatureDate Field Name: SIG_Borrower_1_1_true_1_BW1Name.eSig.eSigDate
Implementation Notes:No user action is required.
EnableEsignatureManifest Added to BSI.Properties
  • Type: Enhancement
  • Reference: PBI 440811
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: As a means to enable or disable the esignature manifest file we have added a flag, EnableEsignatureManifest, to BSI.Properties. With the default of FALSE, Expere does not look for the esigmanifest file as part of the content. When set to TRUE, the esigmanifest file is expected to be in the content repository.
 
Implementation Notes:No user action is required.
Version Number Added to Schemas
  • Type: Enhancement
  • Reference: PBI 442215
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No external-facing tools user documentation; all Expere request and response schemas.
Summary: We have included a version number in all Expere request and response schemas, such as ApiTypes.xsd and PackageAndDocSet.xsd; this will help users identify the version of schema with which they are working.
Note: The schema version number is synonymous with the Expere Engine version number.
Technical notes: A sample version number resembles the following (see version= below):
<xs:schema 
xmlns="http://schemas.bankerssystems.com/2004/ExpereAPI/ExpereIEServices" 
xmlns:xs="http://www.w3.org/2001/XMLSchema" 
targetNamespace="http://schemas.bankerssystems.com/2004/ExpereAPI/ExpereIEServices" 
elementFormDefault="qualified" attributeFormDefault="unqualified" 
version="17.1.0.4255">
Implementation Notes: No user action is required.
New ApplyPoliciesAndReturnTransaction API introduced
  • Type: New Feature
  • Reference: PBI 432140
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: ApplyPoliciesAndReturnTransaction
Summary: The ApplyPoliciesAndReturnTransaction API has been implemented to update the provided transaction with the provided Product information. This allows users to pass the updated returned transaction (which includes the Product information) into our DocViewer application, as well as the ability to use Select, SelectAndGenerate, or Generate API's to generate documents with product data.
Implementation Notes: See ApplyPoliciesAndReturnTransaction for detailed information on using this new API.
Ancillary Barcodes Not Rendering on Dynamic Documents
  • Type: Defect
  • Reference: PBI 443195
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: Ancillary barcodes contained in a request would not render on dynamic documents.
Solution: This did not impact static documents. This has been repaired so requests with ancillary barcodes will render as expected on dynamic documents.
Implementation Notes: No user action is required.
Expere Engine: Pinyon Script added to JetFonts.xml
  • Type: Enhancement
  • Reference: PBI 437588
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: We have added Pinyon Font to the jetfonts.xml file within our Expere Engine. This will allow users to generate a static document with a script font.
Implementation Notes: No user action is required.
Text string area message enhanced
  • Type: Enhancement
  • Reference: PBI 406465
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously if a <Text/> element's text string contained more characters than what was allowed, an error message was logged. We have updated the logging level for this message to be WARN instead of ERROR.
Implementation Notes: No user action is required.
Logging levels updated
  • Type: Enhancement
  • Reference: PBI 432256
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Previously, all exceptions that appeared in our log files were reported as errors. This did not reflect the nature nor severity of the exception being logged.
Technical Notes: We have modified our level of logging to consist of the following:
  • Fatal: major system outage or SQL exception
  • Error: system error that does not set off an alert; retries; ongoing system issue
  • Warning: transactions with invalid GUID format, permissions issues, invalid characters being passed in, invalid transaction xml, etc
Implementation Notes: No user action is required.